the latest commit has the fix for issue 384

Just a question, [this is on prod as well]

Scenario: when the fee amount is changed from default to fast for example, is it expected, when I reopen the advanced settings for the regular button to be active? Should't the lastly used button, be active - in my case it was fast button?

when clearing the fee amount input (btc transactions and ordinal transactions) and hitting apply the NaN value is displayed. We should handle it similarly like we do for stx transactions, which is if the input is cleared it should fallback to default or to display an error message.

when clearing the fee amount input (btc transactions and ordinal transactions) and hitting apply the NaN value is displayed. We should handle it similarly like we do for stx transactions, which is if the input is cleared it should fallback to default or to display an error message.

Screen.Recording.2023-05-05.at.00.09.44.mov

#358
an issue is opened for this. we can prioritise this in the next sprint . but a separate PR can be made for this

Just a question, [this is on prod as well]

Scenario: when the fee amount is changed from default to fast for example, is it expected, when I reopen the advanced settings for the regular button to be active? Should't the lastly used button, be active - in my case it was fast button?

Screen.Recording.2023-05-04.at.23.52.36.mov

you're right. the experience can be made better by storing the state. we can create an issue for this and deal it along with issue #358

This can be merged.
The last two comments will be addressed in issue #358
I'll link to them